home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Night Owl 6
/
Night Owl's Shareware - PDSI-006 - Night Owl Corp (1990).iso
/
033a
/
maxjm110.zip
/
MAXJM110.DOC
< prev
Wrap
Text File
|
1991-05-20
|
4KB
|
85 lines
┌─────────────────────────────┐
│ MAXJM a JModem Interface │
│ MAXIMUS / OPUS │
└─────────────────────────────┘
Version 1.10
Written by Ray Kaliss of
1:141/840fidonet.org.
Hacked on by Randy Edwards
First off, there's no guarantees of any kind with this software. Use it at
your own risk!
Here is a JModem interface for OPUS and MAXIMUS compatible BBS systems. The
other JModem interfaces I tried didn't work for me ... so I wrote my own that
did work for me ... maybe it will work for you.
Install JModem into MAX as an external Protocol. Note: JModem is a single
file transfer protocol, so make sure not to install it as a Maximus "batch"
protocol. Have the EXE called be this one -- MAXJM.EXE. MAXJM must be named
exactly that in order to work.
In operation: when MAX drops out ... it will write MAXJM.CTL ... which
MAXJM.EXE will read ... then it will call JMBATCH.* and pass it the proper
info. JMBatch in turn calls the real JMODEM protocol. MAXJM.LOG is created
if the file transfer was successful so MAX can update the appropriate
statistics.
If anything goes wrong, MAXJM returns several various DOS errorlevels. Though
these are hard or impossible to trap inside of Maximus or Opus, they're useful
for fixing a problem in a 'standalone' mode from DOS.
ErrorLevel returned Meaning
255 = Bad parameter passed. Programmer's error that should never happen.
Contact the author if it does.
254 = Error reading MaxJM.CTL file created by Maximus/Opus. Unlikely to
happen. If it does happen, something has corrupted the MAXJM.CTL file
or the file is in the wrong format.
253 = Unspecified error while doing the DOS shell. Out of memory probably,
perhaps couldn't find COMSPEC variable, etc.
252 = Error opening MaxJM.CTL file -- i.e. file not found. An error here
would point to a BBS installation problem.
1 = Everything went okay except the JModem file transfer aborted.
Trivial, can be ignored as MAXJM and the BBS will take care of it.
0 = All successful. Successful shell to JMBatch.* done and file was
transferred successfully.
See the sample JMBATCH file and edit it to suit yourself.
Notes about JMBATCH: JMBATCH is the file that actually calls the JMODEM file
transfer program. MAXJM will pass JMBATCH two parameters: first, a S or R to
tell JModem whether it's receiving or sending, and secondly the filename it is
to send or receive. Simple, eh?
JModem creates no log files itself. In order to tell whether a file transfer
is successful or not, JModem returns a DOS errorlevel. The JMBATCH file
should "trap" or detect this errorlevel. If an errorlevel is returned a file
called MAXJM.FLG (the FLG for 'flag') should be created. MAXJM will check for
the MAXJM.FLG file created by an aborted file transfer and act accordingly.
MAXJM will then delete the MAXJM.FLG file automatically.
If you don't bother to go to the trouble of trapping JModem for an aborted
transfer and never make any MAXJM.FLG file, then MAXJM won't mind at all -- it
will just think that every file transfer was successful. Of course your users
who are charged download credits for aborted file transfers might be a little
annoyed at this. <grin>
Hey ... it works for me.